System and method for applying vehicle settings in a vehicle

ABSTRACT

A method and system for applying vehicle settings to a vehicle. The method and system include receiving a device identification (ID) from at least one of: a first portable device and a second portable device. The method and system additionally include identifying a user settings profile that is associated to the device ID. The method and system also include determining if the user settings profile has been updated since a last ignition cycle of the vehicle. The method and system further include applying the user settings profile to control a vehicle system, wherein the user settings profile is retrieved from at least one of: a central user settings data repository, a telematics unit of the vehicle, and a head unit of the vehicle.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of, and claims priority to, U.S.application Ser. No. 15/468,251, filed on Mar. 24, 2017, and nowpublished as U.S. Pub. No. 2017/0197631 which is a continuation of, andclaims priority to, U.S. application Ser. No. 14/859,405, filed on Sep.21, 2015, and now issued as U.S. Pat. No. 9,643,619, both applicationsof which are expressly incorporated herein by reference.

BACKGROUND

Many vehicles today include vehicle systems and features that can beadjusted based on user preferences associated with one or more driversand/or passengers. The user preferences can be utilized to adjustvarious settings of the features of vehicle systems in order to providea customized environment within the vehicle for the driver and/orpassenger. In many instances, a vehicle is shared by multiple driversthat each have a different set of driver settings that need to beadjusted within the vehicle based on which driver is operating thevehicle. In some cases, the drivers modify the vehicle settings alreadyimplemented within the vehicle. Determining which set of driver settingsto apply can be a complicated process especially when multiple driversof the vehicle each utilize and modify driver settings to be applied tothe same vehicle.

SUMMARY

According to one aspect, a computer-implemented method for applyingvehicle settings to a vehicle. The method includes receiving a deviceidentification (ID) from at least one of: a first portable device and asecond portable device. The method also includes identifying a usersettings profile that is associated to the device ID. The methodadditionally includes determining if the user settings profile has beenupdated since a last ignition cycle of the vehicle. The method furtherincludes applying the user settings profile to control a vehicle system,wherein the user settings profile is retrieved from at least one of: acentral user settings repository, a telematics unit of the vehicle, anda head unit of the vehicle.

According to a further aspect, a system for applying vehicle settings toa vehicle. The system includes a vehicle settings logic application thatis executed on a head unit of the vehicle. The system also includes adevice identification module that is included as a module of the vehiclesettings logic application that receives a device identification (ID)from at least one of: a first portable device and a second portabledevice. The system additionally includes a settings profileidentification module that is included as a module of the vehiclesettings logic application that identifies a user settings profile thatis associated to the device ID. Additionally, the system includes, asettings profile version control module that is included as a module ofthe vehicle settings logic application that determines if the usersettings profile has been updated since a last ignition cycle of thevehicle. The system further includes a vehicle control module that isincluded as a module of the vehicle settings logic application thatapplies the user settings profile to control a vehicle system whereinthe user settings profile is retrieved from at least one of: a centraluser settings repository, a telematics unit of the vehicle, and a headunit of the vehicle.

According to still another aspect, a non-transitory computer-readablestorage medium is provided that stores instructions that, when executedby a computer, causes the computer to perform a method. The instructionsinclude receiving a device identification (ID) from at least one of: afirst portable device and a second portable device. The instructionsalso include identifying a user settings profile that is associated tothe device ID. The instructions additionally include determining if theuser settings profile has been updated since a last ignition cycle ofthe vehicle. The instructions further include applying the user settingsprofile to control a vehicle system, wherein the user settings profileis retrieved from at least one of: a central user settings repository, atelematics unit of the vehicle, and a head unit of the vehicle.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic view of an exemplary operating environment of avehicle settings decision logic system for applying vehicle settings ina vehicle according to an exemplary embodiment of the presentdisclosure;

FIG. 2 is a process flow diagram of a method to store thecreated/updated user settings profile at one or more components of thesystem, according to an exemplary embodiment of the present disclosure;

FIG. 3 is a process flow diagram of a method for identifying a usersettings profile that is associated to a device ID that is stored at oneor more components of the system, according to an exemplary embodimentof the present disclosure;

FIG. 4 is a process flow diagram of a method for applying a usersettings profile stored on at one or more components of the system,according to an exemplary embodiment of the present disclosure; and

FIG. 5 is a process flow diagram of a method for applying vehiclesettings to the vehicle, according to an exemplary embodiment of thepresent disclosure.

DETAILED DESCRIPTION

The following includes definitions of selected terms employed herein.The definitions include various examples and/or forms of components thatfall within the scope of a term and that can be used for implementation.The examples are not intended to be limiting.

A “bus,’ as used herein, refers to an interconnected architecture thatis operably connected to transfer data between computer componentswithin a singular or multiple systems. The bus can be a memory bus, amemory controller, a peripheral bus, an external bus, a crossbar switch,and/or a local bus, among others. The bus can also be a vehicle bus thatinterconnects components inside a vehicle using protocols such asController Area network (CAN), Media Oriented System Transport (MOST),Local Interconnect Network (LIN), among others.

“Computer communication,” as used herein, refers to a communicationbetween two or more computing devices (e.g., computer, personal digitalassistant, cellular telephone, network device) and can be, for example,a network transfer, a file transfer, an applet transfer, an email, ahypertext transfer protocol (HTTP) transfer, and so on. A computercommunication can occur across, for example, a wireless system (e.g.,IEEE 802.11), an Ethernet system (e.g., IEEE 802.3), a token ring system(e.g., IEEE 802.5), a local area network (LAN), a wide area network(WAN), a point-to-point system, a circuit switching system, a packetswitching system, among others.

An “input device,” as used herein can include devices for controllingdifferent vehicle features which include various vehicle components,systems, and subsystems. The term “input device” includes, but it notlimited to: push buttons, rotary knobs, and the like. The term “inputdevice” additionally includes graphical input controls that take placewithin a user interface which can be displayed by various types ofmechanisms such as software and hardware based controls, interfaces, orplug and play devices.

A “memory,” as used herein can include volatile memory and/ornonvolatile memory. Non-volatile memory can include, for example, ROM(read only memory), PROM (programmable read only memory), EPROM(erasable PROM) and EEPROM (electrically erasable PROM). Volatile memorycan include, for example, RAM (random access memory), synchronous RAM(SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rateSDRAM (DDR SDRAM), and direct RAM bus RAM (DRRAM).

A “module,” as used herein, includes, but is not limited to, hardware,firmware, software in execution on a machine, and/or combinations ofeach to perform a function(s) or an action(s), and/or to cause afunction or action from another module, method, and/or system. A modulecan include a software controlled microprocessor, a discrete logiccircuit, an analog circuit, a digital circuit, a programmed logicdevice, a memory device containing executing instructions, and so on.

An “operable connection,” as used herein can include a connection bywhich entities are “operably connected”, is one in which signals,physical communications, and/or logical communications can be sentand/or received. An operable connection can include a physicalinterface, a data interface and/or an electrical interface.

An “output device,” as used herein can include devices that can derivefrom vehicle components, systems, subsystems, and electronic devices.The term “output devices” includes, but is not limited to: displaydevices, and other devices for outputting information and functions.

A “processor,” as used herein, processes signals and performs generalcomputing and arithmetic functions. Signals processed by the processorcan include digital signals, data signals, computer instructions,processor instructions, messages, a bit, a bit stream, or other meansthat can be received, transmitted and/or detected. Generally, theprocessor can be a variety of various processors including multiplesingle and multicore processors and co-processors and other multiplesingle and multicore processor and co-processor architectures. Theprocessor can include various modules to execute various functions.

A “vehicle,” as used herein, refers to any moving vehicle that iscapable of carrying one or more human occupants and is powered by anyform of energy. The term “vehicle” includes, but is not limited to:cars, trucks, vans, minivans, SUVs, motorcycles, scooters, boats,personal watercraft, and aircraft. In some cases, a motor vehicleincludes one or more engines.

A “vehicle system,” as used herein can include, but are not limited to,any automatic or manual systems that can be used to enhance the vehicle,driving and/or safety. Exemplary vehicle systems include, but are notlimited to: an electronic stability control system, an anti-lock brakesystem, a brake assist system, an automatic brake prefill system, a lowspeed follow system, a cruise control system, a collision warningsystem, a collision mitigation braking system, an auto cruise controlsystem, a lane departure warning system, a blind spot indicator system,a lane keep assist system, a navigation system, a transmission system,brake pedal systems, an electronic power steering system, visual devices(e.g., camera systems, proximity sensor systems), a climate controlsystem, an electronic pretensioning system, among others.

Referring now to the drawings, wherein the showings are for purposes ofillustrating one or more exemplary embodiments and not for purposes oflimiting the same, FIG. 1 is a schematic view of an exemplary operatingenvironment of a vehicle settings decision logic system 100 for applyingvehicle settings in a vehicle. In an exemplary embodiment, the vehiclesettings decision logic system 100 can be utilized to determine one of aplurality of predetermined user settings that are digitally created inthe form of one or more user settings profiles to be stored on andapplied from one of a plurality of components in order to adjustprogrammable functions of one or more vehicle systems. The vehiclesettings decision logic system 100 can identify one of a plurality ofuser settings profiles that are created by a user (e.g., driver of thevehicle) and that are associated to one or more portable devices inorder to ensure that the appropriate set of user preferences are appliedfor the user utilizing the vehicle. The components of the system 100, aswell as the components of other systems, hardware architectures, andsoftware architectures discussed herein, can be combined, omitted ororganized into different architecture for various embodiments. However,the exemplary embodiments discussed herein focus on the environment asillustrated in FIG. 1, with corresponding system components, and relatedmethods.

As shown in FIG. 1, the vehicle settings decision logic system 100provides an overview showing the communications and data transfersbetween a vehicle 102 that executes a vehicle settings logic application104, a first portable device (a mobile computing device) 106, a secondportable device (a smart key device) 108, and an external serverinfrastructure 110 that includes one or more external servers. In anexemplary embodiment, the vehicle settings logic application 104provides a decision logic for applying one of a plurality of usersettings profiles that include user customized settings that areutilized to adjust one or more programmable functions (e.g., settings)of one or more vehicle systems 114 according to one of the plurality ofuser settings profiles. In one embodiment, the user settings profilesare individual data files that contain programming code that can beinterpreted by the vehicle settings logic application 104 to providecommands to adjust the programmable functions of the vehicle system(s)114.

In an exemplary embodiment, each mobile computing device 106 and smartkey device 108 of the system 100 includes a corresponding deviceidentification (ID). As discussed in more detail below, the device IDcan be a unique identifier that can be utilized by the vehicle settingslogic application 104 to determine if one or more of the mobilecomputing devices 106 and/or the smart key devices 108 are connected tothe vehicle 102. In one embodiment, the device ID can be received andevaluated at the time when a driver of the vehicle 102 enables a vehicleignition switch (turns the vehicle ignition to an accessory batterypowered or engine ON state) in order to determine if the mobilecomputing device 106 and/or the smart key device 108 are utilized by oneor more users when using the vehicle 102. The vehicle settings logicapplication 104 can be utilized by a user to create or update(create/update) a user settings profile and further associate thecreated/updated user settings profile to his/her mobile computing device106 and/or smart key device 108. Additionally the user settings logicapplication 104 provides customized settings that are applicable to thevehicle system(s) 114 when the driver enables the ignition of thevehicle 102 based on the receipt of the device ID(s) that arespecifically associated to the applied user settings profile. Forexample, the vehicle settings logic application 104 can receive andutilize the device ID corresponding to a driver's mobile computingdevice 106 to determine if/when the driver is utilizing (carrying,using) the mobile computing device 106 when he/she drives the vehicle102 in order to apply the driver's user settings profile based on thereceipt of the device ID from the driver's mobile computing device 106.

The vehicle 102 of the remote vehicle settings control system 100 caninclude a head unit 112, the vehicle systems 114, an electronic controlunit (ECU) 116, a telematics control unit (TCU) 118, and a communicationunit 120. In one embodiment, the ECU 116 can include internal processingmemory, an interface circuit, and bus lines for transferring data,sending commands, and communicating with the vehicle systems 114.Generally, the ECU 116 includes a processor and memory (not shown).

In one embodiment, the ECU 116 operably controls one or more vehiclesystems 114 based on the application of the selected user settingsprofile by the vehicle settings logic application 104. The vehiclesystems 114 can include (individual vehicle systems not shown), but arenot limited to an audio system, climate control system, infotainmentsystem, navigation system, telecommunications system, vehicle ergonomicssystem, vehicle safety system, etc.

In one embodiment, the communication unit 120 included within thevehicle 102 is capable of providing wired or wireless computercommunications utilizing various protocols to send/receive electronicsignals within the vehicle 102 and to external devices including themobile computing device 106, the smart key device 108, that are directlyconnected (e.g., through a Bluetooth connection, radio frequencyconnection, proximity sensing connection, etc.) to the vehicle 102, whenthe vehicle ignition is enabled. Additionally, the communication unit120 is operably connected for internal computer communication via a bus(e.g., a Controller Area Network (CAN) or a Local Interconnect Network(LIN) protocol bus) to facilitate data input and output between thecomponents of the vehicle 102. For instance, the communication unit 120can be utilized for sending data internally within the vehicle 102between the ECU 116, the head unit 112, the TCU 118, and the vehiclesystems 114.

In an exemplary embodiment, the head unit 112 of the vehicle 102 can beutilized to store hardware and software related to various vehiclesystems 114. In one embodiment, the head unit 112 includes a separatestorage 122 and a controller (not shown) that controls the processes ofthe head unit 112. The storage 122 of the head unit 112 can includevarious types of memory, as described above. In another embodiment, thehead unit 112 is exclusively controlled by the ECU 116. The head unit112 can be utilized to store and execute software corresponding to oneor more vehicle systems 114 that are included as part of the head unit112 and/or throughout the vehicle 102. The storage 122 can be utilizedto store one or more operating systems, applications, application files,vehicle system and subsystem interface data, and the like that can beexecuted by the controller of the head unit 112 and/or the ECU 116. Inone embodiment, the head unit 112 can also include a display unit (notshown) that can be utilized to display one or more user interfaces thatare executed from one or more operating systems, applications, etc. thatare stored on the storage 122 of the head unit 112. In an exemplaryembodiment, the storage 122 of the head unit 112 can store one or moredata files that can be utilized by one or more applications that areexecuted by the controller of the head unit 112 and/or the ECU 116 inorder to adjust programmable features of the vehicle systems 114. Forexample, as discussed in more detail below, the storage 122 of the headunit 112 can store one or more user settings profiles (e.g., data files)that can be utilized by the vehicle settings logic application 104executed on the head unit 112 in order to control the one or morevehicle systems 114.

In an exemplary embodiment, the TCU 118 of the vehicle 102 can be anexternal interface for mobile communication between the vehicle 102 andan external server infrastructure 110 through an internet cloud. In oneembodiment, the TCU 118 can include a telematics communication device124 that is capable of utilizing a GSM, GPRS, Wi-Fi, WiMax, or LTEwireless connection to send and receive one or more data files from themobile computing device 106 and/or external server infrastructure 110directly through the cloud. The TCU 118 can also include storage 126that can include various types of memory (as described above withreference to the storage 122), and a microcontroller (not shown) thatcontrols the processes of the TCU 118. In an exemplary embodiment, thestorage 126 of the TCU 108 can store one or more data files that can beutilized by one or more applications that are executed by the head unit112 and/or the ECU 116 in order to adjust programmable features of thevehicle systems 114. For example, as discussed in more detail below, thestorage 126 of the TCU 118 can store one or more user settings profiles(e.g., data files) that can be utilized by the vehicle settings logicapplication 104 executed on the head unit 112 in order to control theone or more vehicle systems 114.

The mobile computing device 106 (first portable device) of the system100 can include, but is not limited to, a handheld device, a mobilecommunication device, a smart phone, a laptop, a tablet, and ane-reader. In some embodiments, the mobile computing device 106 includesa display screen (not shown), a memory (not shown), and a communicationdevice (not shown). In one embodiment, the memory of the first portabledevice 106 can be utilized to store the user settings profile(corresponding to the user) and the corresponding device identification(ID) that is utilized by the vehicle settings logic application 104 todetermine when the mobile computing device 106 directly connects to thecommunication unit 120 of the vehicle 102.

In one embodiment, the device ID of each mobile computing device 106 caninclude a unique identification code that is created by the vehiclesettings logic application 104 and is stored on the memory of the mobilecomputing device 106 in order to identify the mobile computing device106. In another embodiment, the device ID can include a serial numbercorresponding to each mobile computing device 106 that is assigned tothe mobile computing device 106 by a manufacturer of the mobilecomputing device 106 and is stored on the memory of the mobile computingdevice 106. Upon connecting to the vehicle 102, the mobile computingdevice 106 can send the device ID to the communication unit 120 to beidentified by the vehicle settings logic application 104. As describedin more detail below, the user can associate the device ID of his/hermobile computing device 106 to his/her user settings profile in orderfor the application 104 to apply customized settings on the functions ofthe vehicle system(s) 114. For example, when the driver of the vehicle102 utilizes his/her mobile computing device 106 to connect to thevehicle 102 as he/she enables the vehicle 102, and the vehicle settingslogic application 104 can control the functions of the vehicle systems114 based on the user preference file that corresponds to the driver viathe associated device ID of the mobile computing device 106.

The smart key device 108 (second portable device) of the system 100 caninclude, but is not limited to, an electronic key fob, a vehicle remote,a smart key, an electronic key chain, etc. that can be utilized tocontrol access to the vehicle 102 (e.g., via smart entry door handles).The smart key device 108 can include memory (not shown) and acommunication device (not shown). The memory of the smart key device 108can include a device ID that is associated to the smart key device 108that is utilized by the vehicle settings logic application 104.

In one embodiment, the device ID of each smart key device 108 caninclude a unique identification code that is created by the vehiclesettings logic application 104 and is stored on the memory of the smartkey device 108 in order to identify the smart key device 108. In anotherembodiment, the device ID can include a serial number corresponding toeach smart key device 108 that is assigned to the smart key device 108by a manufacturer of the vehicle 102 or the smart key device 108 and isstored on the memory of the smart key device 108. Upon connecting to thevehicle 102, the mobile computing device 106 can send the device ID tothe communication unit 120 to be identified by the vehicle settingslogic application 104. As described in more detail below, the user canassociate the device ID of the smart key device 108 to his/her usersettings profile in order for the application 104 to apply customizedsettings on the functions of the vehicle systems 114 when the smart keydevice 108 connects to the vehicle 102. For example, when the driver ofthe vehicle 102 utilizes his/her smart key device 108 to enable thevehicle 102, the vehicle settings logic application 104 can control thefunctions of the vehicle systems 114 based on the user preference filethat corresponds to the driver via the associated device ID of thedriver's smart key device 108.

In one embodiment, the external server infrastructure 110 can include aplurality of interconnected servers that support and maintain data thatcan be sent to the telematics communication device 124 of the TCU 118and can be further utilized by one or more components of the vehicle102. The external server infrastructure 110 can include but is notlimited to web servers, data servers, database servers, domaincontrollers, backup servers, and the like. In an exemplary embodiment,the external server infrastructure 110 can include a central usersettings data repository 128. As explained in more detail below, in oneembodiment, the central user settings data repository 128 can beutilized to store one or more user settings profiles that correspond toone or more users that are applied by the vehicle settings logicapplication 104.

In an exemplary embodiment shown in FIG. 1, the vehicle settings logicapplication 104 can be executed on the head unit 112 of the vehicle 102and can be accessed by the driver via the display unit of the head unit112 and/or the mobile computing device 106. In one embodiment, thevehicle settings logic application 104 can be a remote softwareapplication that is installed directly onto the mobile computing device106 that interfaces with a host software application that is executed onthe head unit 112 of the vehicle 102. In another embodiment, the vehiclesettings logic application 104 and/or one or more components of thevehicle settings logic application 104 can be installed and executedexternally from the head unit 112 and/or the mobile computing device 106on a personal computing device (not shown) (e.g., personal computer,laptop, etc.). In some embodiments, the vehicle settings logicapplication 104 can include a web based application that can be executedon the external server infrastructure 110 and can be accessed by thevehicle 102, the mobile computing device 106, and/or the personalcomputing device through a web browser interface. In other embodiments,the vehicle settings logic application 104 can include a cloud basedapplication that is executed on the external server infrastructure 110and that is accessed through a viewer application that is installed onthe storage 122 of the head unit 112 and/or the memory of the mobilecomputing device 106.

In an exemplary embodiment, the vehicle settings logic application 104includes various modules, discussed in detail below. Each user (e.g.,driver of the vehicle 102) can utilize the vehicle settings logicapplication 104 to create an individual user settings profile. Inaddition to creating a user settings profile, the vehicle settings logicapplication 104 can be utilized by each user to update a pre-existing(already created and utilized) user settings profile within the vehicle102 in order to modify the user's customized settings already associatedto the programmable features of the vehicle system(s) 114.

In an exemplary embodiment, the user's mobile computing device 106and/or the user's smart key device 108 are connected to the vehicle 102.The vehicle settings logic application 104 can identify and apply theuser settings profile according to the user's preferences in orderadjust programmable features of the vehicle system(s) 114. For example,the vehicle settings logic application 104 can apply a driver's usersettings profile in order to adjust settings that include audio systemoptions, navigation system options, seat positioning options, mirrorpositioning options, lighting options, door lock options, audio alerts,visual alerts, etc., based on the user's preferences. Therefore, if auser associates his/her user settings profile to his/her mobilecomputing device 106 and/or smart entry device 108, when the user entersthe vehicle 102 and the mobile computing device 106 and/or smart entrydevice 108 connects to the vehicle 102, the user settings profile thatis associated to the mobile computing device 106 and/or smart entrydevice 108 will be applied in order to control the programmable featuresof the vehicle system(s) 114 according to the user's preferences.

In one embodiment, the vehicle settings logic application 104 includes auser interface 130 that can be utilized by each user to create and/orupdate his/her user settings profile. In addition, the user interface130 can be utilized by each user to associate his/her user settingsprofile to one or both of the user's mobile computing device 106 and/orthe smart key device 108. In one embodiment, the user interface 130includes a user settings interface that provides the user with theability to customize the programmable features of one or more of thevehicle systems 114 and store those customized settings into a new (bycreating a user settings profile) or preexisting (by updating a usersettings profile) user settings profile.

In one embodiment, the user interface 130 is presented on the displayscreen of the head unit 112 in order for the user to create/updatehis/her user settings profile directly from the vehicle 102. Asdiscussed, the vehicle settings logic application 104 and the userinterface 130 can also be accessed and displayed on the mobile computingdevice 106. Upon creation of the user settings profile, the user canutilize the user interface 130 on (the display unit of) the head unit112, (the display unit of) the personal computing device or the mobilecomputing device 106 to associate the user settings profile to themobile computing device 106 and/or the smart key device 108 in order forthe user settings profile to be executed when the user enters thevehicle 102 with one of the corresponding devices 106, 108.

As an illustrative example, ‘Driver A’ can create a user settingsprofile on her mobile computing device 106 and can associate the newlycreated user settings profile to the device IDs of her mobile computingdevice 106 and her smart key device 108 (e.g., a first key fob of thevehicle 102) to be utilized when ‘Driver A's’ mobile computing device106 and/or the smart key device 108 connects to the vehicle 102 (whenshe enters the vehicle 102 with the respective devices 106, 108).Similarly, ‘Driver B’ can create a user settings profile on the headunit 112 and can associate the newly created user settings profile tothe device ID of his smart key device 108 (e.g., a second key fob of thevehicle 102) to be utilized when ‘Driver B's’ smart key device 108connects to the vehicle 102 (when he enters the vehicle 102 with hissmart key device 108).

Referring again to FIG. 1, in an exemplary embodiment, a settingsprofile storage module 132 of the vehicle settings logic application 104is utilized to store the newly created/update user settings profilesthat were created/updated by a driver on the user interface 130 at oneor more components of the system 100. As will be discussed below, in anexemplary embodiment, the settings profile storage module 132 determinesa location to store the driver's user settings profile based on theuser's utilization of the mobile computing device 106 or the head unit112 of the vehicle 116 to create/update the user settings profile.

Referring now to FIG. 2, a process flow diagram of a method 200 to storethe created/updated user settings profile at one or more components ofthe system 100 is illustrated. FIG. 2 will be described with referenceto the components of FIG. 1, though it is to be appreciated that themethod of FIG. 2 can be used with other systems and/or components. In anexemplary embodiment, the method 200 is executed by the settings profilestorage module 132 of the vehicle settings logic application 104. Atblock 202, the method includes determining if the user settings profilewas created or updated (by the user) on the mobile computing device 106(via the user interface 130). In one embodiment, the settings profilestorage module 132 classifies the created/updated user settings profileas being created by the user through the mobile computing device 106,the head unit 112 of the vehicle 102, or the personal computing device.At block 204, if it is determined that the user settings profile wascreated/updated on the mobile computing device 106 (at block 202), themethod includes associating the user settings profile to a device ID ofthe mobile computing device 106 that is used to create/update the usersettings profile. For example, when the user utilizes the user interface130 to create/update his/her user settings profile through the his/hermobile computing device 106, the user settings profile is automaticallyassociated to the device ID of the user's mobile computing device 106.

The method proceeds to block 206, where the method includes determiningif the ignition switch of the vehicle 102 is enabled and the mobilecomputing device 106 is directly connected to the vehicle 102. In oneembodiment, the settings profile storage module 132 can utilize thecommunication device of the mobile computing device 106 to send a pingsignal to the communication unit 120 in order determine if the vehicleignition is in an accessory battery powered state or an engine ON stateand that the mobile computing device 106 is in range to directly connectto the communication unit 120 of the vehicle 102. Specifically, if thevehicle ignition is enabled, (i.e., the vehicle 102 is receiving power)and the communication unit 120 received the ping signal (i.e., themobile computing device 106 was located within a range of the vehicle102 that a direct connection could occur), the communication unit 120can receive the ping signal and can transmit a return signal to thecommunication device of the mobile computing unit 106. Upon receipt ofthe return signal, the settings profile storage module 132 determinesthat the ignition switch is enabled and that the mobile computing device106 can directly connect to the vehicle 102. In other words, when thevehicle ignition switch is enabled, the communication unit 120 of thevehicle 102 is capable of directly connecting and communicating (e.g.,via a Bluetooth connection) with the communication device of the mobilecomputing device 106, in order to directly transmit the user settingsprofile to the head unit 112 of the vehicle 102 and apply the usersettings profile to the vehicle 102. Otherwise, when the ignition switchof the vehicle 102 is disabled, the vehicle 102 does not receive anypower, and/or the mobile computing device 106 is not within a range todirectly connect to the vehicle 102, the mobile communication device 106cannot directly transmit the user settings profile to the head unit 112of the vehicle 102.

If it is determined that the ignition switch of the vehicle 102 is notenabled and the mobile computing device 106 cannot directly connect tothe vehicle 102 (at block 206), at block 208, the method includesstoring the user settings profile on the TCU 118 and the central usersettings data repository 128. In one embodiment, upon the settingsprofile storage module 132 determining that the mobile computing device106 cannot directly connect to the vehicle 102, the settings profilestorage module 132 can utilize the communication device of the mobilecomputing device 106 to send the user settings profile to the TCU 118and the central user settings data repository 128 via the externalserver infrastructure 110. In one embodiment, the mobile computingdevice 106 can send the user settings profile via the wirelessconnection (e.g., Wi-Fi, 4G, LTE, etc.) to the external serverinfrastructure 110 on the cloud to be stored on the central usersettings data repository 128. In one example, the user settings profilestorage module 132 can utilize the telematics communication device 124of the TCU 118 to obtain (via the wireless connection) the user settingsprofile from the central settings data repository 128 of the externalserver infrastructure 110 on the cloud to store the user settingsprofile on the storage 124 of the TCU 118. In another example, the usersettings profile storage module 132 can utilize the telematicscommunication device 124 of the TCU 118 to directly communicate with thecommunication device of the mobile computing device 106 (via thewireless connection) to obtain the user settings profile from the mobilecomputing device 106 to be stored on the storage 124 of the TCU 118.

In another embodiment, if the settings profile storage module 132 storesthe user settings profile on the TCU 118 (at block 208), the settingsprofile storage module 132 transfers a copy of the user'screated/updated user settings profile to the storage 122 of head unit112 from the storage 124 of the TCU 118. As will be described in moredetail below, the created/updated user settings profile stored on thehead unit 112 can be applied to the vehicle 102 by the vehicle settingslogic application 104, when the device ID of the smart key device 108 isreceived by the device identification module 134 and the device ID ofthe mobile computing device 106 is not received by the deviceidentification module 134 (i.e., the smart key device 108 is connectedto the vehicle 102 and the mobile computing device 106 is not connectedto the vehicle 102 when the ignition of the vehicle 102 is enabled).

If it is determined that the ignition switch of the vehicle 102 isenabled and the mobile communication device can directly connect to thevehicle 102 (at block 206), at block 210, the method includes storingthe user settings profile on the head unit 112 and the central usersettings data repository 128. Specifically, upon determining that themobile computing device 106 can directly connect to the communicationunit 120 of the vehicle 102, the settings profile storage module 132(created on and associated to the mobile computing device 106) storesthe user preference settings file associated to the mobile computingdevice 106 directly to the storage 122 of the head unit 112 of thevehicle 102. For example, if a driver utilizes his/her mobile computingdevice 106 to update his/her user settings profile, the settings profilestorage module 132 stores the updated user preference file on the headunit 112 to be further evaluated as discussed in more detail below. Inone embodiment, the user settings profile can also be sent via thewireless connection (e.g., Wi-Fi, 4G, LTE, etc.) from the communicationdevice of the mobile computing device 106 to the external serverinfrastructure 110 on the cloud to be stored on the central usersettings data repository 128. This embodiment ensures that the usersettings profile associated with the user that is stored on the centraluser settings data repository 128 is the most recently updated copy ofthe user settings profile. In another embodiment, the user settingsprofile is additionally stored on the memory of the mobile computingdevice 106.

At block 212, the method includes prompting the user to associate a usersettings profile to a device ID of a smart key device 108. Specifically,the settings profile storage module 132 can utilize the user interface130 on the (display of the) mobile computing device 106 to prompt theuser to associate (the device ID of) his/her smart key device 108 of thevehicle 102 to the user settings profile that is created/updated by theuser on the mobile computing device 106. In one embodiment, the userinterface 130 can communicate with the communication unit 120 in orderto provide the user a list of a plurality of smart key devices 108 thatwere previously paired to the vehicle 102 (by the vehicle manufacturer,dealer, etc.)

Referring again to block 202 of FIG. 2, if it is determined that theuser settings profile is not created/updated on the mobile computingdevice 106, at block 214, the method includes prompting the user toassociate a user settings profile to a device ID of a mobile computingdevice 106 and/or a smart key device 108. In an exemplary embodiment,upon the user creating his/her user settings profile on the head unit112 (e.g., the display unit of the head unit 112), the settings profilestorage module 132 utilizes the user interface 130 on the head unit 112to prompt the user to associate/re-associate (the device ID of) theuser's mobile computing device 106 and/or smart key device 108 to theuser settings profile that is created/updated by the user. In oneembodiment, the user interface 130 can present a list of mobilecomputing devices 106 with corresponding device IDs that have beenconnected to the communication unit 120 of the vehicle 102 in the past(e.g., via a Bluetooth connection). The user interface 130 canadditionally present a list of smart key devices 108 that werepreviously paired to the vehicle 102 (by the vehicle manufacturer,dealer, etc.) In another embodiment, the user interface 130 can presenta list of one or more connected (via a direct connection to the vehicle102) mobile computing devices 106 and/or smart key devices 108 that caneach be selected by the user to associate to his/her user settingsprofile. For example, if the communication unit 120 connects to a mobilecomputing device 106 via a Bluetooth connection and a smart key device108 via a radio frequency connection, the user interface 130 can presentboth devices 106, 108 on the list in order for the user to associate oneor both of them to his/her user settings profile.

At block 216, the method includes determining if the user settingsprofile was created/updated on the head unit 112. In one embodiment, asdiscussed, the settings profile storage module 132 classifies thecreated/updated user settings profile as being created by the userthrough the mobile computing device 106, the head unit 112 of thevehicle 102, or the personal computing device. If it is determined thatthe user settings profile was created on the head unit 112 (at block216), at block 218, the method includes storing the user settingsprofile on the head unit 112 and the central user settings datarepository. In one embodiment, when the settings profile storage module132 determines that the user settings profile is classified as beingcreated by the driver on the user interface 130 on head unit 112 (e.g.,the display unit of the head unit 112, the settings profile storagemodule 132 stores the user settings profile created/updated by the useron the head unit 112 directly on the storage 122 of the head unit 112).For example, if a driver utilizes the display unit of the head unit 112to update his/her user settings profile and associates his/her usersettings profile to the device ID of the mobile computing device 106 andthe device ID of a smart key device 108, the vehicle profile storagemodule 120 stores the user preference file directly on the storage 122of the head unit 112 to be further evaluated when the mobile computingdevice 106 and/or the smart key device 108 associated to the usersettings profile are directly connected to the vehicle 102. Therefore,the settings profile storage module 132 ensures that the user settingsprofile is stored at one or more specific locations based on utilizationof the mobile computing device 106 or the head unit 112 to create/updatethe user settings profile. The user settings profile can also be sentvia the wireless connection (e.g., Wi-Fi, 4G, LTE, etc.) from thecommunication device of the mobile computing device 106 when it isconnected to the vehicle 102. Specifically, the mobile communicationdevice 106 can be utilized by the vehicle 102 to connect to the externalserver infrastructure 110 on the cloud in order to store the usersettings profile on the central user settings data repository 128. In analternate embodiment, the settings profile storage module 132 can alsoutilize the telematics communication device 124 to communicate with theexternal server infrastructure 110 through the cloud in order to accessthe user settings profile transferred directly from the mobile computingdevice 106 and stored on the central user settings data repository 128to be downloaded to the head unit 112.

If it is determined that the user settings profile was not created onthe head unit 112 (at block 216), at block 220, the method includesstoring the user settings profile on the central user settings datarepository 128. In one embodiment, when the settings profile storagemodule 132 determines that the user settings profile was notcreated/updated by the driver on the head unit 112 (at block 220), thesettings profile storage module 132 determines that the user settingsprofile was created by the user on the personal computing device. Whenthe user settings profile is created/updated on the personal computingdevice, the user settings profile is stored directly on the central usersettings data repository 128 of the external server infrastructure 110from the personal computing device.

Referring back to FIG. 1, as discussed above, upon the creation orupdate of the user settings profile on the mobile computing device 106,the head unit 112, and/or the personal computing device by the user, acopy of the user settings profile is sent to the external serverinfrastructure 110 in order to be stored on the central user settingsdata repository 128. In other words, the vehicle settings logicapplication 104 ensures that the central user settings data repository128 always stores the latest updated version of the user settingsprofile created on the mobile computing device 106, the head unit 112,or the personal computing device. Also as discussed below, with respectto FIG. 4 (block 426), the system 100 also ensures that any usersettings profile that is applied to adjust the settings of one or morevehicle systems 114 is saved to the central user setting data repository128 to ensure that the central user settings data repository 128 storesthe most recently utilized version of the user settings profile.

In one or more embodiments, when the user settings profile iscreated/updated on the personal computing device and the latest copy ofthe user settings profile is sent and stored on the central usersettings data repository 128, upon the connection of the mobile device106 to the vehicle 102, the communication device of the mobile device106 can connect to the external server infrastructure 110 on the cloudvia the wireless connection in order to download the latest updatedversion of the user settings profile to be stored on the mobile device106 and on the storage 126 of the TCU 118. In addition, the latestupdated version of the user settings profile can be transferred to thehead unit 112 to be stored on the storage 122. This functionalityensures that there is synchronization with regards to the version of theuser settings profile between the mobile computing device 106, the TCU118, the head unit 112, and the central user settings data repository128.

In one embodiment, if the user creates/updates his/her user settingsprofile on the head unit 112 (at block 216), the user settings profilecan be sent to the TCU 118 to be stored on the storage 126.Additionally, the telematics communication device 124 of the TCU 118 orthe communication device of mobile computing device 106 that isconnected to the vehicle 102 can be utilized to connect to externalserver infrastructure 110 on the cloud via the wireless connection inorder to store a copy of the user settings profile created/updated onthe head unit 112 to the central user settings data repository 128. Inone or more embodiments, when the user settings profile iscreated/updated on the head unit 112 and the latest copy of the usersettings profile is sent and stored on the central user settings datarepository 128, the communication device of the mobile computing device106 connects to the external server infrastructure 110 on the cloud viathe wireless connection in order to download the latest updated copy ofthe user settings profile. This functionality also ensures that there issynchronization with regards to the version of the user settings profilebetween the mobile computing device 106, the TCU 118, the head unit 112,and the central user settings data repository 128.

In an exemplary embodiment, the vehicle settings logic application 104also includes a plurality of modules utilized to apply the user settingsprofile that is stored by the settings profile storage module 132 asdiscussed above. The vehicle settings logic application 104 includes adevice identification module 134 that is utilized to determine if one ormore mobile computing devices 106 and/or smart key devices 108 aredirectly connected to the vehicle 102. For example, when a driver entersthe vehicle 102 with a mobile computing device 106 and/or the smart keydevice 108, upon the connection from the mobile computing device 106and/or the smart key device 108 to the vehicle 102, the deviceidentification module 134 receives the device ID from the mobilecomputing device 106 and/or the smart key device 108.

In one embodiment, the device identification module 134 communicateswith the communication unit 120 in order to receive one or more deviceIDs (sent) from the connected mobile computing device 106 and/or theconnected smart key device 108. More specifically, when the driver ofthe vehicle enables the vehicle ignition (using a smart key device 108,the mobile computing device 106 and/or a push button), the ECU 116 cansend an electronic signal to the device identification module 134. Uponreceipt of the electronic signal from the ECU 116 that indicates thevehicle ignition switch is enabled, the device identification module 134can utilize the communication unit 120 of the vehicle 102 to determineif the mobile computing device 106 and/or the smart key device 108 isconnected to the vehicle 102 by receiving one or more device IDs of anymobile computing device(s) 106 and/or smart key device(s) 108 connectedto the communication unit 120 of the vehicle 102. For example, if thedriver's mobile computing device 106 is connected to the communicationunit 120 of the vehicle 102 (e.g., via a Bluetooth connection) when thevehicle ignition switch is enabled, the communication unit 120 suppliesthe device ID of the driver's mobile communication device 106 to thedevice identification module 134.

Similarly, if the driver's smart key device 108 is connected to thecommunication unit 120 of the vehicle 102 (e.g., via a radio frequencyconnection) when the vehicle ignition switch is enabled, thecommunication unit 120 supplies the device ID of the driver's smart keydevice 108 to the device identification module 134. In an exemplaryembodiment, upon receipt of the device ID of the connected mobilecomputing device 106 and/or the connected smart key device 108, thedevice identification module 134 supplies the one or more device IDs toa settings profile identification module 136 of the vehicle settingslogic application 104.

In the exemplary embodiment shown in FIG. 1, the settings profileidentification module 136 can identify a user settings profile that isassociated to the device ID of the connected mobile computing device 106and/or the connected smart key device 108. The user settings profile canbe stored on the mobile computing device 106, the TCU 118, the head unit112, and/or the central user settings data repository 128 as determinedby the device identification module 134 (per the method 200 of FIG. 2).In some embodiments, once the device identification module 134 utilizesthe communication unit 120 of the vehicle 102 to determine the deviceID(s) of the mobile computing device(s) 106 and/or the smart keydevice(s) 108 connected to the vehicle 102, the settings profileidentification module 136 identifies the copy of the user settingsprofile that is associated to the device ID of the mobile computingdevice 106 and/or the smart key device 108. Specifically, the settingsprofile identification module 136 identifies a copy of the user settingsprofile stored at one or more locations (e.g., mobile computing device106, TCU 118, head unit 112, central user settings data repository 128)in order to further evaluate the identified user settings profile todetermine which version of the user settings profile to apply, asdiscussed in more detail below. For example, when the user createdhis/her user settings profile, if the settings profile storage module132 stored the driver's user settings profile on the mobile computingdevice 106 (at step 210 of FIG. 2) and on the head unit 112 (at step 220of FIG. 2), the settings profile identification module 136 identifieswhich copy of the driver's user settings profile to further evaluate.

Referring now to FIG. 3, a process flow diagram of a method 300 foridentifying a user settings profile that is associated to a device IDthat is stored at one or more components of the system 100. FIG. 3 willbe described with reference to the components of FIG. 1, though it is tobe appreciated that the method of FIG. 3 can be used with other systemsand/or components. In an exemplary embodiment, the method 300 isexecuted by the settings profile identification module 136 of thevehicle settings logic application 104.

At block 302, the method includes determining if the user settingsprofile was created/updated on the mobile computing device 106. In oneembodiment, the settings profile identification module 136 cancommunicate with the settings profile storage module 132 to determine ifthe user utilized the mobile computing device 106 to create/update theuser settings profile.

If it is determined that the user settings profile was created/updatedon the mobile computing device 106 (at block 302), at block 304, themethod includes determining if the ignition switch of the vehicle 102 isenabled and the mobile computing device 106 is directly connected to thevehicle 102. In one embodiment, as described above, the settings profilestorage module 132 can utilize the communication device of the mobilecomputing device 106 to send the ping signal to the communication unit120 in order determine if the vehicle ignition is in an accessorybattery powered state or an engine ON state and that the mobilecomputing device 106 is in range to directly connect to thecommunication unit 120 of the vehicle 102.

If it is determined that the ignition switch is not enabled and themobile computing device 106 is not directly connected to the vehicle 102(at block 304), at block 306, the method includes identifying the usersettings profile that is associated to the device ID of the mobilecomputing device 106 that is stored on the TCU 118. Specifically, thesettings profile identification module 136 communicates with thesettings profile storage module 132 to determine that the user settingsprofile that is associated to the device ID of the mobile computingdevice 106 is stored on the storage 126 of the TCU 118. As described inmore detail below, the settings profile identification module 136 canidentify the user settings profile on the TCU 118 to be furtherevaluated by the settings profile version control module 138 todetermine if the user settings profile was created/updated since a lastignition cycle of the vehicle 102.

If it is determined that the ignition switch is enabled and the mobilecomputing device 106 is directly connected to the vehicle 102, at block308, the method includes identifying the user settings profile that isassociated to the device ID of the mobile computing device 106 and/orthe smart entry device 108 that is stored on the head unit 112. In oneembodiment, the settings profile identification module 136 communicateswith the settings profile storage module 132 to determine that the usersettings profile that was created/updated on the mobile computing device106 and is associated to the device ID of the mobile computing device106 and/or the smart entry device 108 is stored on the storage 122 ofthe head unit 112 (based on the settings profile storage module 132storing the user settings profile on the head unit 112 directly from themobile computing device at block 210 of FIG. 2).

Referring again to block 302, if it is determined that the user settingsprofile was not created/updated on the mobile computing device 106, atblock 310, it is further determined if the user settings profile wascreated/updated on the head unit 112. In one embodiment, the settingsprofile identification module 136 can communicate with the settingsprofile storage module 132 to determine if the user utilized the headunit 112 or personal computing device to create/update the user settingsprofile, since it is already determined that the user did not utilizethe mobile computing device 106 to create/update the user settingsprofile.

If it is determined that the user settings profile was created/updatedon the head unit 112 (at block 310), at block 308, the method includesidentifying the user settings profile that is associated to the deviceID of the mobile computing device 106 and/or the smart entry device 108that is stored on the head unit 112. In one embodiment, the settingsprofile identification module 136 communicates with the settings profilestorage module 132 to determine that the user settings profile that wascreated/updated on the head unit 112 and is associated to the device IDof the mobile computing device 106 and/or the smart entry device 108 isstored on the storage 122 of the head unit 112 (based on the settingsprofile storage module 132 storing the user settings profile on the headunit 112 at block 218 of FIG. 2).

If it is determined that the user settings profile was notcreated/updated on the head unit 112 (at block 310), at block 312, themethod includes identifying the user settings profile that is associatedto the device ID of the mobile computing device 106 and/or the smartentry device 108 that is stored on the central user settings datarepository 128. In one embodiment, the settings profile identificationmodule 135 communicates with the settings profile storage module 132 todetermine that the user settings profile was created on the personalcomputing device and is associated to the device ID of the mobilecomputing device 106 and/or the smart entry device 108 that is stored onthe central user settings data repository 128.

Referring again to FIG. 1, in an exemplary embodiment, the settingsprofile identification module 136 prioritizes the user settings profilethat is associated to the mobile computing device 106 over the usersettings profile that is associated to the smart key device 108.Consequently, if both the mobile computing device 106 and the smart keydevice 108 are determined to be connected to the vehicle 102, thesettings profile identification module 136 ensures the user settingsprofile that is associated to the device ID of the mobile computingdevice 106 is identified to be further evaluated by the settings profileversion control module 138. Therefore, if the user settings profile thatis associated to the mobile computing device 106 (that is connected tothe vehicle 102) is different (is from another user) than the usersettings profile that is associated to the smart key device 108 (that isconnected to the vehicle 102), the user settings profile that isassociated to the mobile computing device 106 will be utilized over theuser settings profile that is associated with the smart key device 108.

As an illustrative example, ‘User A’ can create a user settings profilethat is associated to the device ID of her mobile computing device 106,and ‘User B’ can create a user settings profile that is associated tothe device ID of his smart key device 108. In a scenario when both ‘UserA’ and ‘User B’ enter the vehicle 102, and their respective devices 106,108 connect to the vehicle 102, the vehicle settings logic application104 will identify the user settings profile associated to User A'smobile computing device 106 to be applied to adjust the programmablefeatures of the vehicle system(s) 114 in accordance to User A'spreferences.

In an exemplary embodiment, the settings profile version control module138 of the vehicle settings logic application 104 is utilized todetermine if the user settings profile that was created/updated by theuser on the mobile computing device 106 and that is identified by thesettings profile identification module 136 on the mobile device 106 orthe TCU 118 has been created/updated (by the user) since the lastignition cycle of the vehicle 102. In some embodiments, when the usersettings profile is created/updated by the user, in addition toassociating the device ID of the mobile computing device 106 and/orsmart key device 108 to the user settings profile, the settings profilestorage module 132 also associates a version number to the user settingsprofile upon storing the user settings profile on the mobile computingdevice 106 and/or the TCU 118.

In an exemplary embodiment, as will be described in more detail below,when the user settings vehicle control module 138 determines that theuser settings profile was created by the user on the mobile computingdevice 106, the user settings vehicle control module 138 determines ifthe identified user setting profile (that was created by the mobilecomputing device 106 and is stored on the mobile computing device 106 orthe TCU 118) has been created/updated since a last ignition cycle of thevehicle 102. Upon determining that the user settings profile wascreated/updated since the last ignition cycle of the vehicle 102, thevehicle settings logic application 104 saves a copy of the user settingsprofile on the storage 122 of the head unit 112 to be applied each timethe vehicle 102 is used until the user settings profile is updated. Inone embodiment, upon applying the user settings profile that was savedto the head unit 112, the vehicle settings logic application 104classifies the user settings profile stored on the head unit 112 as a‘pre-existing’ user settings profile.

In some embodiments, upon the determination that the usercreated/updated the user settings profile on the mobile computing device106, the settings profile version control module 138 also determines ifthe version of the pre-existing user settings profile stored on the headunit 112 matches the version (and the associated device ID) of the usersettings profile that is identified by the settings profileidentification module 136 (that is stored on the mobile computing device106 or the TCU 118). In an exemplary embodiment, each time the vehicleignition switch is enabled, the settings profile version control module138 communicates with the settings profile storage module 132 in orderto determine if the user created the user settings profile on the mobilecomputing device 106 or on the head unit 112 (e.g., via the display unitof the head unit 112). In one embodiment, when the settings profileversion control module 138 determines that the user settings profile iscreated by the user on the mobile computing device 106, the settingsprofile version control module 138 can determine if the user settingsprofile was created/updated since the last ignition cycle of the vehicle102. In one embodiment, the settings profile version control module 138can determine that the user settings profile has been created/updatedsince the last ignition cycle of the vehicle 102 when it is determinedthat the pre-existing user settings profile (that was applied prior tothe last ignition cycle of the vehicle 102) stored on the head unit 112is an earlier version than (and is associated to the same device ID as)the user settings profile identified by the settings profileidentification module 136. On the other hand, the settings profileversion control module 138 can determine that the user settings profilehas been created/updated prior to the last ignition cycle of the vehicle102 when it is determined that the pre-existing user settings profile(that was applied prior to the last ignition cycle of the vehicle 102)stored on the head unit 112 matches the version of (and is associated tothe same device ID as) the user settings profile identified by thesettings profile identification module 136.

In an additional embodiment, when the user settings profile iscreated/updated by the user on the mobile computing device 106, inaddition to associating the device ID to the user settings profile, thesettings profile storage module 132 also associates a time stampindicator that signifies when the user settings profile wascreated/updated by the user. In one embodiment, the ECU 116 can includea log that logs the time of each ignition cycle (each specific time thevehicle 102 was enabled), the settings profile version control module138 can communicate with the ECU 116 to determine the time of the lastignition cycle. Upon determining the time of the last ignition cycle,the settings profile version control module 138 can analyze the timestamp associated with the user settings profile identified by thesettings profile identification module 136 (as being stored on themobile computing device 106 or the TCU 118) in order to determine if theuser settings profile was updated since the last ignition cycle of thevehicle 102.

In an exemplary embodiment, the settings profile version control module138 communicates with a vehicle control module 140 of the vehiclesettings logic application 104 to apply the created/updated usersettings profile from the mobile computing device 106, the TCU 118, thehead unit 112, the central user settings data repository 128 or thepre-existing user settings profile from the head unit 112 based on thedetermination by the settings profile version control module 138 thatthe user settings profile was created/updated on the head unit 112, orthe personal computing device or if the user settings profile that wascreated on the mobile computing device 112 has been updated since thelast ignition cycle of the vehicle 102.

Referring now to FIG. 4, a process flow diagram of a method 400 forapplying a user settings profile stored on at one or more components ofthe system 100 is shown. FIG. 4 will be described with reference to thecomponents of FIG. 1, though it is to be appreciated that the method ofFIG. 4 can be used with other systems/components. In an exemplaryembodiment, the method 400 is executed by the vehicle control module 140of the vehicle settings logic application 104 each time an ignitioncycle of the vehicle 102 occurs (e.g., when the driver of the vehicle102 turns the vehicle 102 to an accessory battery powered or engine ONstate).

At block 402, the method includes determining if the device ID of themobile computing device 106 is received. In one embodiment, the settingsprofile identification module 136 communicates with the deviceidentification module 134 to determine if the device identificationmodule 134 received a device ID from the user's mobile computing device110. As described above, when the vehicle ignition is enabled, thedevice identification module 134 receives the device ID of the connectedmobile computing device 106 and/or smart key device 108. Specifically,upon connecting to the communication unit 120 of the vehicle 102, themobile computing device 106 sends the corresponding device ID to thecommunication unit 120 in order for the device identification module 132to identify the connected mobile computing device 106. In other words(at block 402), the settings profile identification module 136determines if the mobile computing device 106 is directly connected tothe communication unit 120 of the vehicle 102.

If it is determined that the device ID of the mobile computing device106 is not received (at block 402), at block 404, it is determined ifthe device ID of the smart entry device 108 is received. Specifically,upon receiving the determination by the settings identification module128 that the device ID of the mobile computing device 106 was notreceived (i.e., the mobile computing device 106 was not connected to thevehicle 102), the settings profile identification module 136communicates with the device identification module 134 to determine ifthe device ID of the smart key device 108 (that is directly connected tothe communication unit 120 of the vehicle 102) is received by thesettings identification module 126.

If it is determined that the device ID of the smart entry device 108 isreceived (at block 404), at block 408, the method includes determiningif the user settings profile was created on the head unit 112. In oneembodiment, the settings profile identification module 136 cancommunicate with the settings profile storage module 132 to determine ifthe user utilized the head unit 112 or personal computing device tocreate/update the user settings profile, since it is already determinedthat the user did not utilize the mobile computing device 106 tocreate/update the user settings profile.

If it is determined that the user settings profile was created/updatedon the head unit 122 (at block 408), at block 412, the method includesdetermining if the user settings profile identified on the head unit hasbeen created/updated since a last ignition cycle of the vehicle 102. Inone embodiment, if the settings profile version control module 138determines that the pre-existing user settings profile is stored on thehead unit 112, the settings profile version control module 138 furtherevaluates the version of the pre-existing user settings profile storedon the head unit 112 to determine if it is a matching version or anearlier version than the identified user settings profile 106 stored onthe central user settings data repository 128. For example, it can bedetermined if the user used the mobile computing device 106 or personalcomputing device to update the user settings profile that was stored onthe central user settings data repository at a point of time after theuse settings profile was stored on the head unit 112.

If it is determined that the user settings profile identified on thehead unit 112 has been not created/updated since a last ignition cycleof the vehicle 102 (at block 412), at block 414, the method includesapplying the pre-existing user settings profile from the head unit 112.Specifically, if the settings profile identification module 136determines that the version of the user settings profile stored on thehead unit 112 is a matching version of the user settings profile that isidentified by the settings profile identification module 136 as storedon the central user settings data repository 128, then the settingsprofile identification module 136 sends a corresponding command to thevehicle control module 140 to apply created/updated user settingsprofile stored on the head unit 112. Therefore, the created/updated usersettings profile associated to the device ID of the smart entry device108 that is stored on the head unit 112 is applied by the vehiclecontrol module 140 in order to adjust the programmable features of thevehicle system(s) 114. Specifically, the vehicle control module 140 cansend a command to the ECU 116 to control the vehicle system(s) 114 basedon the user settings profile associated to the device ID of the user'ssmart key device 108 that is identified by the device identificationmodule 134 (e.g., when the user entered the vehicle 102). In analternate embodiment, the vehicle control module 140 can access theexternal server infrastructure 110 via a connection from the mobilecomputing device 106 or the TCU 118 in order to apply the user settingsprofile stored on the central user settings data repository 128.

The method proceeds to block 424, wherein the method includes saving theuser settings profile to the central user settings data repository 128.In one embodiment, the wireless connection (e.g., Wi-Fi, 4G, LTE, etc.)can be established from the communication device of the mobile computingdevice 106 to the external computing infrastructure 110 when the mobilecomputing device 106 is connected to the vehicle 102 in order to storethe user settings profile that was applied from the head unit 112 on thecentral user settings data repository 128. In another embodiment, thevehicle control module 140 can utilize the telematics communicationdevice 124 of the TCU 118 to send a copy of the created/updated usersettings profile that was applied from the head unit 112 to the centraluser settings data repository 128 of the external server infrastructure110 (e.g., via Wi-Fi, 4G, LTE, etc.) Therefore, the external serverinfrastructure 100 stores the most recently applied copy of the usersettings profile associated to the device ID of the smart key device 108(received by the device identification module 134).

Referring back to block 412, if it is determined that the user settingsprofile identified on the head unit has been created/updated since alast ignition cycle of the vehicle 102, at block 416, the methodincludes applying the created/updated user settings profile from thecentral user settings data repository 128. Specifically, thecommunications device of the mobile computing device 106 or thetelematics communication device 124 of the TCU 118 can be utilized towirelessly connect (e.g., Wi-Fi, 4G, LTE, etc.) to the external serverinfrastructure 110 on the cloud to transfer the user settings profile tothe communication unit 120 of the vehicle 102 to be executed by the ECU116 to control the one or more vehicle systems 114.

Referring back to block 408, if it is determined that the user settingsprofile was not created/updated on the head unit 122, at block 422, themethod includes applying the created/updated user settings profile fromthe central user settings data repository 128. In one embodiment, thevehicle control module 140 can apply the updated version of thecreated/updated user settings profile that was saved on the central usersettings data repository 128 when the user created/updated his/her usersettings profile. Specifically, the communications device of the mobilecomputing device 106 or the telematics communication device 124 of theTCU 118 can be utilized to wirelessly connect (e.g., Wi-Fi, 4G, LTE,etc.) to the external server infrastructure 110 on the cloud to transferthe user settings profile to the communication unit 120 of the vehicle102 to be executed by the ECU 116 to control the one or more vehiclesystems 114.

At block 424, the method includes saving the user settings profile tothe central user settings data repository 128. In one embodiment, uponapplying the user settings profile directly from the central usersettings data repository 128, the vehicle control module 140 can alsoutilize the communication device of the mobile computing device 106 orthe telematics communication device 124 of the TCU 118 to resave a copyof the updated/created user settings profile that is applied from thecentral user settings data repository 128 back to the central usersettings data repository 128 of the external server infrastructure 110on the cloud. The resaving of the user settings profile can ensure thatthe version of the user settings profile stored on the central usersettings data repository 128 includes an updated time stamp based on thetime of its application. In some embodiments, the vehicle control module140 can further save the user settings profile as a pre-existing usersettings profile on the storage 122 of the head unit 112.

Referring again to block 402, if the method determines that the deviceID of the mobile computing device 106 is received, at block 406, themethod includes determining if the user settings profile wascreated/updated on the mobile computing device 106. In one embodiment,settings profile version control module 140 communicates with thesettings profile storage module 132 in order to determine if the usercreated the user settings profile on the mobile computing device 106.

If it is determined that the user settings profile was notcreated/updated on the mobile computing device 106 (at block 406), themethod once again returns to block 408, wherein the method includesdetermining if the user settings profile was created on the head unit112. Specifically, the settings profile identification module 136 cancommunicate with the settings profile storage module 132 to determine ifthe user utilized the head unit 112 or personal computing device tocreate/update the user settings profile that is associated to the deviceID of the mobile computing device 106.

If it is determined that the user settings profile was created/updatedon the head unit 112 (at block 408), at block 412 the method includesdetermining if the user settings profile identified on the head unit hasbeen created/updated since a last ignition cycle of the vehicle 102. Inone embodiment, if the settings profile version control module 138determines that the pre-existing user settings profile is stored on thehead unit 112, the settings profile version control module 138 furtherevaluates the version of the pre-existing user settings profile storedon the head unit 112 to determine if it is a matching version or anearlier version than the identified user settings profile 106 stored onthe central user settings data repository 128.

If it is determined that the user settings profile identified on thehead unit 112 has been not created/updated since a last ignition cycleof the vehicle 102 (at block 412), at block 414, the method includesapplying the pre-existing user settings profile from the head unit 112.In one embodiment, when the device identification module 134 determinesthat device ID of the mobile computing device 106 is received, thesettings profile storage module 132 communicates to the vehicle controlmodule 140 that the user settings profile associated with the device IDof the mobile computing device 106 is stored on the head unit 112, sincethe user created/update his/her user settings profile on the head unit112 (e.g., the display unit of the head unit 112). Additionally, it isdetermined that the user associated his/her user settings profile to thedevice ID of the mobile computing device 106. Therefore, thecreated/updated user settings profile associated to the device ID of themobile computing device 106 that is stored on the head unit 112 isapplied by the vehicle control module 140 in order to adjust theprogrammable features of the vehicle system(s) 114. Specifically, thevehicle control module 140 can send a command to the ECU 116 to controlthe vehicle system(s) 114 based on the user settings profile associatedto the device ID of the user's mobile computing device 106 that isidentified by the device identification module 134 (e.g., when the userentered the vehicle 102).

The method proceeds to block 424, wherein the method includes saving theuser settings profile to the central user settings data repository 128.In one embodiment, the wireless connection (e.g., Wi-Fi, 4G, LTE, etc.)can be established from the communication device of the mobile computingdevice 106 to the external computing infrastructure 110 when the mobilecomputing device 106 is connected to the vehicle 102 in order to storethe user settings profile that was applied from the head unit 112 on thecentral user settings data repository 128. In another embodiment, thevehicle control module 140 can utilize the telematics communicationdevice 124 of the TCU 118 to send a copy of the created/updated usersettings profile that was applied from the head unit 112 to the centraluser settings data repository 128 of the external server infrastructure110 (e.g., via Wi-Fi, 4G, LTE, etc.) Therefore, the external serverinfrastructure 100 stores the most recently applied copy of the usersettings profile associated to the device ID of the mobile computingdevice 106.

Referring back to block 412, if it is determined that the user settingsprofile identified on the head unit has been created/updated since alast ignition cycle of the vehicle 102, at block 416, the methodincludes applying the created/updated user settings profile from thecentral user settings data repository 128. Specifically, thecommunications device of the mobile computing device 106 or thetelematics communication device 124 of the TCU 118 can be utilized towirelessly connect (e.g., Wi-Fi, 4G, LTE, etc.) to the external serverinfrastructure 110 on the cloud to transfer the user settings profile tothe communication unit 120 of the vehicle 102 to be executed by the ECU116 to control the one or more vehicle systems 114. In some embodiments,the vehicle control module 140 can further save the user settingsprofile as a pre-existing user settings profile on the storage 122 ofthe head unit 112.

Referring back to block 408, if it is determined that the user settingsprofile was not created/updated on the head unit 122, at block 422, themethod includes applying the created/updated user settings profile fromthe central user settings data repository 128. In one embodiment, thevehicle control module 140 can apply the updated version of thecreated/updated user settings profile that is associated to the deviceID of the mobile computing device 106 and that was saved on the centraluser settings data repository 128 when the user created/updated his/heruser settings profile. Specifically, the communications device of themobile computing device 106 or the telematics communication device 124of the TCU 118 can be utilized to wirelessly connect (e.g., Wi-Fi, 4G,LTE, etc.) to the external server infrastructure 110 on the cloud totransfer the user settings profile to the communication unit 120 of thevehicle 102 to be executed by the ECU 116 to control the one or morevehicle systems 114. In some embodiments, the vehicle control module 140can further save the user settings profile as a pre-existing usersettings profile on storage 122 of the head unit 112.

Referring again to block 406, if it is determined that the user settingsprofile was created/updated on the mobile computing device 106, at block410, the method includes determining if the user settings profile isidentified on the head unit 112. In one embodiment, the settings profileversion control module 138 communicates with the settings profileidentification module 136 in order to determine if the user settingsprofile associated with the device ID of the user's mobile computingdevice 106 is identified on the head unit 112.

If it is determined that the user settings profile is identified on thehead unit 112 (at block 410), at block 412, the method includesdetermining if the user settings profile identified on the head unit 112has been created/updated since a last ignition cycle of the vehicle 102.In one embodiment, if the settings profile version control module 138determines that the pre-existing user settings profile is stored on thehead unit 112, the settings profile version control module 138 furtherevaluates the version of the pre-existing user settings profile storedon the head unit 112 to determine if it is a matching version or anearlier version than the identified user settings profile 106 stored onthe central user settings data repository 128.

If it is determined that the user settings profile identified on themobile computing device has not been created/updated since a lastignition cycle of the vehicle 102 (at block 412), at block 414, themethod includes applying the pre-existing user settings profile from thehead unit 112. Specifically, if the settings profile identificationmodule 136 determines that the version of the pre-existing user settingsprofile (that was applied by the vehicle control unit 140 prior to thelast ignition cycle of the vehicle 102) stored on the central usersettings data repository 128 matches the version of the user settingsprofile that is identified by the settings profile identification module136 as stored on the head unit 112, then the settings profileidentification module 136 sends a corresponding command to the vehiclecontrol module 140 to apply the pre-existing user settings profilestored on the head unit 112. The vehicle control module 140 applies thepre-existing user settings profile (that corresponds to the device ID ofthe device 106 recognized by the device identification module 134) fromthe head unit 112 of the vehicle 102.

The method proceeds to block 424, wherein the method includes saving theuser settings profile to the central user settings data repository 128.In one embodiment, the wireless connection (e.g., Wi-Fi, 4G, LTE, etc.)can be established from the communication device of the mobile computingdevice 106 to the external computing infrastructure 110 when the mobilecomputing device 106 is connected to the vehicle 102 in order to storethe user settings profile that was applied from the head unit 112 on thecentral user settings data repository 128. In another embodiment, thevehicle control module 140 can utilize the telematics communicationdevice 124 of the TCU 118 to send a copy of the created/updated usersettings profile that was applied from the head unit 112 to the centraluser settings data repository 128 of the external server infrastructure110 (e.g., via Wi-Fi, 4G, LTE, etc.) Therefore, the external serverinfrastructure 100 stores the most recently applied copy of the usersettings profile associated to the device ID of the smart key device 108(received by the device identification module 134).

Referring again to block 412, if it is determined that the user settingsprofile identified on the head unit 112 has been created/updated since alast ignition cycle of the vehicle 102, at block 416, the methodincludes applying the created/updated user settings profile from thecentral user settings data repository 128. In one embodiment, thesettings profile identification module 136 determines that the versionof the pre-existing user settings profile stored on the head unit 112 isan earlier version of the identified user settings profile stored on thecentral user settings data repository 128, then the settings profileidentification module 136 sends a corresponding command to the vehiclecontrol module 140 to apply the updated user settings profile stored onthe central user settings data repository 128.

The method proceeds to block 424, wherein the method includes saving theuser settings profile to the central user settings data repository 128.In one embodiment, upon applying the user settings profile directly fromthe central user settings data repository 128, the vehicle controlmodule 140 can also utilize the communication device of the mobilecomputing device 106 or the telematics communication device 124 of theTCU 118 to resave a copy of the updated/created user settings profilethat is applied from the central user settings data repository 128 backto the central user settings data repository 128 of the external serverinfrastructure 110 on the cloud. The resaving of the user settingsprofile can ensure that the version of the user settings profile storedon the central user settings data repository 128 includes an updatedtime stamp based on the time of its application.

Referring again to block 410, if it is determined that the user settingsprofile is not identified on the head unit 112, at block 418, the methodincludes determining if the user settings profile is identified on theTCU 118 has been created/updated since a last ignition cycle of thevehicle 102. In one embodiment, if the settings profile version controlmodule 138 determines that the pre-existing user settings profile isstored on the TCU 118, the settings profile version control module 138further evaluates the version of the pre-existing user settings profilestored on the TCU 118 to determine if it is a matching version or anearlier version than the identified user settings profile 106 stored onthe central user settings data repository 128. In some embodiments, thevehicle control module 140 can further save the user settings profile asa pre-existing user settings profile on the storage 122 of the head unit112.

If it is determined that the user settings profile identified on the TCU118 has been created/updated since a last ignition cycle of the vehicle102 (at block 418), at block 416, the method applies the created/updateduser settings profile from the central user settings data repository128. Specifically, if the settings profile identification module 136determines that the version of the pre-existing user settings profile(that was applied by the vehicle control unit 140 prior to the lastignition cycle of the vehicle 102) stored on the central user settingsdata repository 128 does not match the version of the user settingsprofile that is identified by the settings profile identification module136 as stored on the TCU 118, then the settings profile identificationmodule 136 sends a corresponding command to the vehicle control module140 to apply the pre-existing user settings profile stored on thecentral user settings data repository 128. The vehicle control module140 applies the pre-existing user settings profile (that corresponds tothe device ID of the device 106 recognized by the device identificationmodule 134) from the central user settings data repository 128.

The method proceeds to block 424, wherein the method includes saving theuser settings profile to the central user settings data repository 128.In one embodiment, upon applying the user settings profile directly fromthe central user settings data repository 128, the vehicle controlmodule 140 can also utilize the communication device of the mobilecomputing device 106 or the telematics communication device 124 of theTCU 118 to resave a copy of the updated/created user settings profilethat is applied from the central user settings data repository 128 backto the central user settings data repository 128 of the external serverinfrastructure 110 on the cloud. The resaving of the user settingsprofile can ensure that the version of the user settings profile storedon the central user settings data repository 128 includes an updatedtime stamp based on the time of its application. In some embodiments,the vehicle control module 140 can further save the user settingsprofile as a pre-existing user settings profile on the storage 122 ofthe head unit 112.

Referring back to block 418, if it is determined that the user settingsprofile identified on the TCU 118 has been not created/updated since alast ignition cycle of the vehicle 102, at block 420, the methodincludes applying the pre-existing user settings profile from the TCU118. Specifically, if the settings profile identification module 136determines that the pre-existing user settings profile is not stored onthe head unit 112 or that the version of the pre-existing user settingsprofile (that was applied by the vehicle control unit 140 prior to thelast ignition cycle of the vehicle 102) stored on the TCU 118 is amatching version of the user settings profile that is identified by thesettings profile identification module 136 as stored on the central usersettings data repository 128, then the settings profile identificationmodule 136 sends a corresponding command to the vehicle control module140 to apply created/updated user settings profile stored on the storage124 of the TCU 118.

The method proceeds to block 424, wherein the method includes saving theuser settings profile to the central user settings data repository 128.In one embodiment, the wireless connection (e.g., Wi-Fi, 4G, LTE, etc.)can be established from the communication device of the mobile computingdevice 106 to the external computing infrastructure 110 when the mobilecomputing device 106 is connected to the vehicle 102 in order to storethe user settings profile that was applied from the head unit 112 on thecentral user settings data repository 128. In another embodiment, thevehicle control module 140 can utilize the telematics communicationdevice 124 of the TCU 118 to send a copy of the created/updated usersettings profile that was applied from the head unit 112 to the centraluser settings data repository 128 of the external server infrastructure110 (e.g., via Wi-Fi, 4G, LTE, etc.) Therefore, the external serverinfrastructure 100 stores the most recently applied copy of the usersettings profile associated to the device ID of the smart key device 108(received by the device identification module 134). In some embodiments,the vehicle control module 140 can further save the user settingsprofile as a pre-existing user settings profile on the storage 122 ofthe head unit 112.

Referring now to FIG. 5, a process flow diagram of a method 500 forapplying vehicle settings to the vehicle 102 is shown. In an exemplaryembodiment, the method 500 is executed by the modules 134-140 of thevehicle settings logic application 104. At block 502, the methodincludes receiving a device ID from at least one of the first portabledevice and a second portable device. As described above, in oneembodiment, the device identification device can receive the device IDfrom the mobile computing device 106 and/or the smart key device 108upon a direct connection of the mobile computing device 106 and/or thesmart key device 108 to the communication unit 120 of the vehicle 102.

At block 504, the method includes identifying a user settings profilethat is associated to the device ID. In one embodiment, as describedabove (in the method 300 of FIG. 3), the settings profile identificationmodule 136 can identify the user settings profile associated to themobile computing device 106 and/or the smart key device 108 (received atblock 502) as being stored on the mobile computing device 106, the TCU118, and/or the head unit 112. At block 506, the method includesdetermining if the user settings profile has been updated since a lastignition cycle of the vehicle 102. In one embodiment, the settingsprofile version control module 138 determines if the user settingsprofile associated to the mobile computing device 106 that is identifiedon the mobile computing device 106 or the TCU 118 has beencreated/updated by the user since the last ignition cycle of the vehicle102.

At block 508, the method includes applying the user settings profile tocontrol a vehicle system. In an exemplary embodiment, as described above(in the method 400 of FIG. 4), the vehicle control module 140 appliesthe user settings profile from the head unit 112, the central usersettings repository 128, or the TCU 118.

As discussed, various embodiments of the vehicle settings decision logicsystem 100 can be utilized. In addition, numerous components andtechnologies that have not been discussed herein can be utilized tocompute operations associated with the vehicle settings logicapplication 104 and to adjust the programmable functions of the vehiclesystem(s) 114 per the user's preferences. It is to be appreciated thatin addition of one or more mobile computing device 106 and/or smart keydevices 108, the vehicle settings logic application 104 can be utilizedon and/or with different types of devices that are in production andthat are not yet in production.

The embodiments discussed herein can also be described and implementedin the context of computer-readable storage medium storingcomputer-executable instructions. Computer-readable storage mediaincludes computer storage media and communication media. For example,flash memory drives, digital versatile discs (DVDs), compact discs(CDs), floppy disks, and tape cassettes. Computer-readable storage mediacan include volatile and nonvolatile, removable and non-removable mediaimplemented in any method or technology for storage of information suchas computer readable instructions, data structures, modules or otherdata. Computer readable storage media excludes non-transitory tangiblemedia and propagated data signals.

It will be appreciated that various implementations of theabove-disclosed and other features and functions, or alternatives orvarieties thereof, can be desirably combined into many other differentsystems or applications. Also that various presently unforeseen orunanticipated alternatives, modifications, variations, or improvementstherein can be subsequently made by those skilled in the art which arealso intended to be encompassed by the following claims.

The invention claimed is:
 1. A computer-implemented method for executingvehicle settings of a vehicle comprising: receiving a deviceidentification (ID) from at least one of: a first portable device and asecond portable device; determining a computing device that is used tocreate or update at least one user settings profile; storing the atleast one user settings profile on at least one of a plurality ofcomponents associated with the vehicle based on the computing devicethat is determined to be used to create or update the at least one usersettings profile, wherein the at least one of the plurality ofcomponents include a head unit of the vehicle, a telematics control unitof the vehicle, and a central user settings data repository; determiningif the user settings profile has been updated since a last ignitioncycle of the vehicle; executing the user settings profile to control avehicle system of the vehicle, wherein the user settings profile isretrieved from at least one of: the central user settings datarepository, the telematics unit of the vehicle, and the head unit of thevehicle, and controlling at least one vehicle system of the vehicle,wherein the at least one vehicle system is controlled based on theexecution of the at least one user settings profile.
 2. Thecomputer-implemented method of claim 1, wherein determining thecomputing device that is used to create or update the at least one usersettings profile includes determining that the at least one usersettings profile is created or updated on the first portable device,wherein the at least one user settings profile is associated to thedevice ID of the first portable device, wherein the first portabledevice includes a mobile phone.
 3. The computer-implemented method ofclaim 2, wherein storing the at least one user settings profile includesdetermining if an ignition switch of the vehicle is enabled and thefirst portable device is connected to the vehicle and storing the atleast one user settings profile on the head unit and the central usersettings data repository.
 4. The computer-implemented method of claim 2,wherein storing the at least one user settings profile includesdetermining if the ignition switch of the vehicle is enabled and thefirst portable device is connected to the vehicle and storing the atleast one user settings profile on the telematics control unit and thecentral user settings data repository when it is determined that theignition switch of the vehicle is disabled and the first portable deviceis not connected to the vehicle.
 5. The computer-implemented method ofclaim 1, wherein determining the computing device that is used to createor update the at least one user settings profile includes determiningthat the at least one user settings profile is created or updated on thehead unit, wherein the at least one user settings profile is associatedto at least one of: the device ID of the first portable device and thedevice ID of the second portable device, wherein the second portabledevice includes a smart entry device.
 6. The computer-implemented methodof claim 5, wherein storing the at least one user settings profileincludes storing the at least one user settings profile on the head unitand the central user settings data repository when it is determined thatthe at least one user settings profile is created or updated on the headunit, wherein the at least one user settings profile is stored on thecentral user settings repository when it is determined that the at leastone user settings profile is not created or updated on the firstportable device and the head unit.
 7. The computer-implemented method ofclaim 1, wherein determining if the at least one user settings profilehas been updated since the last ignition cycle of the vehicle includescomparing a version of the at least one user settings profile stored onthe central user settings data repository with a version of the at leastone user settings profile stored on at least one of: the head unit andthe telematics control unit and determining if the at least one usersettings profile is at least one of: an updated user settings profilethat is stored on the central user settings data repository that hasbeen created or updated since the last ignition cycle of the vehicle,and a pre-existing user settings profile that is stored on at least oneof: the head unit and the telematics control unit that has been createdor updated since the last ignition cycle of the vehicle.
 8. Thecomputer-implemented method of claim 7, wherein executing the at leastone user settings profile includes determining that the first portabledevice is connected to the vehicle based on receiving the device ID fromthe first portable device, wherein the updated user settings profileassociated with the device ID of the first portable device that isstored on the central user settings repository is executed when it isdetermined that the pre-existing user settings profile has been createdor updated since it was stored on at least one of: the head unit and thetelematics control unit, otherwise the pre-existing user settingsprofile associated with the device ID of the first portable device thatis stored on at least one of the: head unit and the telematics controlunit is executed.
 9. The computer-implemented method of claim 7, whereinexecuting the at least one user settings profile includes determiningthat the second portable device is connected to the vehicle based onreceiving the device ID from the second portable device and determiningthat the first portable device is not connected to the vehicle, whereinthe at least one user settings profile that is executed includes atleast one of: an updated user settings profile associated with thedevice ID of the second portable device that is stored on the centraluser settings data repository and a pre-existing user settings profileassociated with the device ID of the second portable device that isstored on at least one of: the head unit and the telematics controlunit, wherein the updated user settings profile associated with thedevice ID of the second portable device that is stored on the centraluser settings repository is executed when it is determined that thepre-existing user settings profile has been created or updated since itwas stored on at least one of: the head unit and the telematics controlunit, otherwise the pre-existing user settings profile associated withthe device ID of the second portable device that is stored on at leastone of the: head unit and the telematics control unit is executed.
 10. Asystem for executing vehicle settings of a vehicle comprising: a memorystoring instructions when executed by a processor cause the processorto: receive a device identification (ID) from at least one of: a firstportable device and a second portable device; determine a computingdevice that is used to create or update at least one user settingsprofile; store the at least one user settings profile on at least one ofa plurality of components associated with the vehicle based on thecomputing device that is determined to be used to create or update theat least one user settings profile, wherein the at least one of theplurality of components include a head unit of the vehicle, a telematicscontrol unit of the vehicle, and a central user settings datarepository; determine if the user settings profile has been updatedsince a last ignition cycle of the vehicle; execute the user settingsprofile to control a vehicle system of the vehicle, wherein the usersettings profile is retrieved from at least one of: the central usersettings data repository, the telematics unit of the vehicle, and thehead unit of the vehicle, and control at least one vehicle system of thevehicle, wherein the at least one vehicle system is controlled based onthe execution of the at least one user settings profile.
 11. The systemof claim 10, wherein determining the computing device that is used tocreate or update the at least one user settings profile includesdetermining that the at least one user settings profile is created orupdated on the first portable device, wherein the at least one usersettings profile is associated to the device ID of the first portabledevice, wherein the first portable device includes a mobile phone. 12.The system of claim 11, wherein storing the at least one user settingsprofile includes determining if an ignition switch of the vehicle isenabled and the first portable device is connected to the vehicle andstoring the at least one user settings profile on the head unit and thecentral user settings data repository.
 13. The system of claim 11,wherein storing the at least one user settings profile includesdetermining if the ignition switch of the vehicle is enabled and thefirst portable device is connected to the vehicle and storing the atleast one user settings profile on the telematics control unit and thecentral user settings data repository when it is determined that theignition switch of the vehicle is disabled and the first portable deviceis not connected to the vehicle.
 14. The system of claim 10, whereindetermining the computing device that is used to create or update the atleast one user settings profile includes determining that the at leastone user settings profile is created or updated on the head unit,wherein the at least one user settings profile is associated to at leastone of: the device ID of the first portable device and the device ID ofthe second portable device, wherein the second portable device includesa smart entry device.
 15. The system of claim 14, wherein storing the atleast one user settings profile includes storing the at least one usersettings profile on the head unit and the central user settings datarepository when it is determined that the at least one user settingsprofile is created or updated on the head unit, wherein the at least oneuser settings profile is stored on the central user settings repositorywhen it is determined that the at least one user settings profile is notcreated or updated on the first portable device and the head unit. 16.The system of claim 10, wherein determining if the at least one usersettings profile has been updated since the last ignition cycle of thevehicle includes comparing a version of the at least one user settingsprofile stored on the central user settings data repository with aversion of the at least one user settings profile stored on at least oneof: the head unit and the telematics control unit and determining if theat least one user settings profile is at least one of: an updated usersettings profile that is stored on the central user settings datarepository that has been created or updated since the last ignitioncycle of the vehicle, and a pre-existing user settings profile that isstored on at least one of: the head unit and the telematics control unitthat has been created or updated since the last ignition cycle of thevehicle.
 17. The system of claim 16, wherein executing the at least oneuser settings profile includes determining that the first portabledevice is connected to the vehicle based on receiving the device ID fromthe first portable device, wherein the updated user settings profileassociated with the device ID of the first portable device that isstored on the central user settings repository is executed when it isdetermined that the pre-existing user settings profile has been createdor updated since it was stored on at least one of: the head unit and thetelematics control unit, otherwise the pre-existing user settingsprofile associated with the device ID of the first portable device thatis stored on at least one of the: head unit and the telematics controlunit is executed.
 18. The system of claim 16, wherein executing the atleast one user settings profile includes determining that the secondportable device is connected to the vehicle based on receiving thedevice ID from the second portable device and determining that the firstportable device is not connected to the vehicle, wherein the at leastone user settings profile that is executed includes at least one of: anupdated user settings profile associated with the device ID of thesecond portable device that is stored on the central user settings datarepository and a pre-existing user settings profile associated with thedevice ID of the second portable device that is stored on at least oneof: the head unit and the telematics control unit, wherein the updateduser settings profile associated with the device ID of the secondportable device that is stored on the central user settings repositoryis executed when it is determined that the pre-existing user settingsprofile has been created or updated since it was stored on at least oneof: the head unit and the telematics control unit, otherwise thepre-existing user settings profile associated with the device ID of thesecond portable device that is stored on at least one of the: head unitand the telematics control unit is executed.
 19. A non-transitorycomputer readable storage medium storing instructions that, whenexecuted by a computer, which includes at least a processor, causes thecomputer to perform a method, the method comprising: receiving a deviceidentification (ID) from at least one of: a first portable device and asecond portable device; determining a computing device that is used tocreate or update at least one user settings profile; storing the atleast one user settings profile on at least one of a plurality ofcomponents associated with a vehicle based on the computing device thatis determined to be used to create or update the at least one usersettings profile, wherein the at least one of the plurality ofcomponents include a head unit of the vehicle, a telematics control unitof the vehicle, and a central user settings data repository; determiningif the user settings profile has been updated since a last ignitioncycle of the vehicle; executing the user settings profile to control avehicle system of the vehicle, wherein the user settings profile isretrieved from at least one of: the central user settings datarepository, the telematics unit of the vehicle, and the head unit of thevehicle, and controlling at least one vehicle system of the vehicle,wherein the at least one vehicle system is controlled based on theexecution of the at least one user settings profile.
 20. Thenon-transitory computer readable storage medium of claim 19, whereinexecuting the at least one user settings profile includes determiningthat the first portable device is connected to the vehicle based onreceiving the device ID from the first portable device, wherein anupdated user settings profile associated with the device ID of the firstportable device that is stored on the central user settings repositoryis executed when it is determined that a pre-existing user settingsprofile has been created or updated since it was stored on at least oneof: the head unit and the telematics control unit, otherwise thepre-existing user settings profile associated with the device ID of thefirst portable device that is stored on at least one of the: head unitand the telematics control unit is executed.